Method for automatically searching for documents related to calendar and email entries

ABSTRACT

A method is provided for enabling a user to search for documents that the user has previously viewed on its local machine. The method may rely upon three main system components: the desktop integration module, the index module, and the graphical user interface module. The desktop integration module is an application which monitors documents with which the user interacts for predetermined events, and obtains content data and metadata from the monitored documents. The index module indexes the content data and metadata received from the desktop integration module. The graphical user interface module then permits a user to utilize the desktop integration module and index module by allowing a user to search for a document.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to the commonly owned U.S. patentapplication Ser. No. 10/910,607, filed Aug. 4, 2004, which issued asU.S. Pat. No. 7,496,563; U.S. patent application Ser. No. 10/910,606,filed Aug. 4, 2004, abandoned; U.S. patent application Ser. No.10/910,568, filed, Aug. 4, 2004, which issued as U.S. Pat. No.7,421,421; U.S. patent application Ser. No. 10/910,641, filed Aug. 4,2004, abandoned; U.S. patent application Ser. No. 10/910,617, filed Aug.4, 2004, which issued as U.S. Pat. No. 7,385,260; U.S. patentapplication Ser. No. 10/910,577, filed Aug. 4, 2004, which issued asU.S. Pat. No. 7,634,461; co-pending U.S. patent application Ser. No.10/910,603, filed Aug. 4, 2004; and U.S. patent application Ser. No.10/910,640, filed Aug. 4, 2004, which issued as U.S. Pat. No. 7,493,303,each filed herewith and incorporated by reference in its entirety.

FIELD OF THE INVENTION

The invention relates to an application for searching a document that auser has previously viewed on user terminal device.

BACKGROUND OF THE INVENTION

Many programs enable a user to search for documents located on thecomputer device. For example, a user may be able to search for adocument by entering search terms believed to reflect the document'stitle or by entering search terms believed to be included in thedocument text. However, conventional document management tools arelimited in the amount of search criteria that a user may use to locate aparticular desired document.

Often, users only remember, or have access to, small bits of informationrelated to the document for which they are searching, such as, forexample, the day and/or approximate time the document was accessed, abroad overview of what the document was about, and/or other details.Users are generally not good at creating search criteria, particularlybased on such limited information, and would be better at modifying asearch if they were give clues to form a more effective search.

It is an aspect of the invention to assist a user with searchingspecifically for documents the user has previously accessed by providingcriteria that might enable the user to more easily locate a particulardesired document.

It is another aspect of the invention to provide a graphical userinterface with various features and functions to facilitate the userwith locating the document once the search has been performed.

SUMMARY OF THE INVENTION

These and other objects are addressed through various embodiments of theinvention. According to one aspect of the invention, a system and methodare provided for quickly and efficiently searching for and selectivelyretrieving one or more documents that a user has previously accessed.The previously accessed documents may or may not be located at theuser's local workstation. As used herein, the term documents may referto files such as, for example, Microsoft Word or Excel documents, emailmessages, web pages, media files, folders, and/or other files.

The system may include a desktop integration module, an index module, agraphical user interface module, and/or other modules. The desktopintegration module may monitor documents with which the user interactsfor predetermined events and obtain content data and metadata from themonitored documents. The index module may index the content data andmetadata received from the desktop integration module. The graphicaluser interface module may then permit a user to utilize the index moduleby allowing a user to search for documents.

The desktop integration module may monitor documents that the userviews, edits, creates, or otherwise accesses for predetermined events.For example, the desktop integration module may track each time a useropens a document and each time the user closes the same document,enabling the duration of document interaction to be determined. Thedesktop integration module may obtain content data, such as keywords,title of the document, author of the document, and/or other control dataand metadata determined from the predetermined events for the monitoreddocuments, and transfer the content data and metadata to the indexmodule.

The index module may index parameters that enable the user to search andfilter the monitored documents. For each document monitored by thedesktop integration module, the index may include parameters such as,for example, the date created, the date opened, the date closed, thedate modified, the amount of time spent on a document, the date printed,the date sent, the number of times of document was accessed, and/orother parameters. The index module may also store keywords from thedocument, the title of the document, and/or the author of the document.These parameters in the index module may be determined from the contentdata and metadata collected by the desktop integration module. A filtermay be provided, enabling user to specify documents that are not to beindexed, such as a default home page or personal email.

The graphical user interface module may enable a user to performsearches of the index created by the index module and therefore locate adocument which has been previously accessed by the user. The resultsreflect documents considered relevant in content based on the searchterms and other parameters entered by the user such as, for example,dates and selected applications. The user may browse the search resultsand/or sort the result set by various criteria for ease of viewing.

According to one aspect of the invention, desktop integration module mayinclude one or more subsystems, such as, for example, applicationplug-ins, a communications module, a user interaction module, a documentfilter module, and/or other modules. The desktop integration module maytrack each instance in which a user enters a URL to access a web page.In some embodiments, the desktop integration module may track web pagesthat a user visits by accessing a link on a page for which a URL wasentered. In other embodiments, the desktop integration module may trackan instance where the user opens a Word document or reads an email.

A document filter module may be provided to enable a user to specifydocuments that should not be monitored or indexed. For example,documents that a user commonly accesses or documents that containprivate information such as, for example, online bank account statementsor webpages with the “https” protocol may be filtered and not indexed.

Application plugins may extract information from documents such as, forexample, document type, content, and/or author. Communications modulemay be used to queue documents being retrieved from application pluginsto the index module. Communications module may also convert documentsfrom their native format, such as, for example, .DOC or .XLS, to acommon XML format. User interaction module may interact with applicationplugins to track the amount of time a user spends interacting with adocument.

According to another aspect of the invention, the graphical userinterface module may present a graphical user interface having multiplegraphical visualizations of a search results set. A calendar may bedisplayed indicating when a user has accessed a document in the searchresults set. A document usage histogram may be displayed illustratingall documents that the user has accessed compared to those documentsmatching the search query.

According to another aspect of the invention, a histogram displayed on agraphical user interface may allow a user to see the context of theresult set against their own document usage. Vertical lines may bepresented indicating documents that match the search query. The verticallines may be of varying heights, indicating the relevance of thedocument to the search query.

According to another aspect of the invention, multiple relatedhistograms may be provided. The histograms may represent the relevanceof the search results, as well as the number of documents matching thesearch criteria for a given day. The histogram may have one axisdisplaying, for example, dates and times, and another axis displaying,for example, the amount of time spent on a particular document.

According to another aspect of the invention, better search results forspecific users may be returned by enhancing the result set rankingsaccording to a specific user's interest in the document. User metricsmay be collected during a user's interaction with other documents toenhance keyword relevance rankings. User metrics may include the timespent on a document, frequency with which the document was viewed,whether the document is printed, and/or other metrics. The amount oftime a user has spent on a document may be measured if one or morecriteria such as, for example, whether the document is in focus and/orwhether some type of input has been received relative to the documentwithin a particular time interval, are met.

According to another aspect of the invention, historical data related toa user's interaction with a document may be provided with a searchresults set. This may allow a user to more readily distinguish betweendocuments in the results set.

A user may view metrics obtained by the desktop integration module byperforming a triggering action, for example, by right-clicking on adocument in the results set or other triggering action. Performing thetriggering action may cause the calendar and histogram views to change,reflecting the additional information.

According to one aspect of the invention, the search system may beembedded into a user's calendar and/or email application. The user maythen generate search queries by performing a triggering action on aselected calendar or email entry. The search query may include, forexample, the title of a meeting, meeting attendees, dates, keywords inthe body of the calendar or email entry, and/or other query options.

According to another aspect of the invention, a system and method may beprovided, enabling users to search a local workstation from anenterprise portal. This may enable the user to search their localworkstation as well as other document management systems simultaneously.An index control program and a web responder may be downloaded to auser's workstation. Documents may then be indexed at the userworkstation and inbound query requests by an enterprise portal servermay be accepted.

A user may perform a search of their workstation through an enterpriseportal. The search query may be processed at the local workstation andresults may be returned in a format compatible with the enterpriseserver.

Other objects and features of the invention will become apparent fromthe following detailed description considered in connection with theaccompanying drawings. The drawings are designed for purposes ofillustration only and the invention is not limited to the particularsshown therein. Various alternatives and modifications within the scopeof the invention will be apparent from the description contained herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a system for searching forpreviously accessed documents, according to an embodiment of theinvention.

FIG. 2 illustrates a graphical user interface, according to anembodiment of the invention.

FIG. 3 illustrates a web portal having an embedded search field,according to an embodiment of the invention.

FIG. 4 is a flowchart illustrating an operation of a desktop integrationmodule, according to an embodiment of the invention.

FIG. 5 illustrates a graphical user interface, according to oneembodiment of the invention.

FIG. 6 illustrates a chronology histogram, according to an embodiment ofthe invention.

FIG. 7 illustrates another chronology histogram, according to anembodiment of the invention.

FIG. 8 illustrates a graphical user interface, according to anembodiment of the invention.

FIG. 9 illustrates a graphical user interface, according to anembodiment of the invention.

FIG. 10 illustrates a results set listing, according to an embodiment ofthe invention.

FIG. 11 illustrates a calendar view from an email program, according toan embodiment of the invention.

FIG. 12 is a block diagram of a system for searching from a remoteportal, according to an embodiment of the invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

According to one embodiment of the invention, a system 100 may beprovided enabling a user to search for and/or selectively retrievedocuments that the user has previously accessed. FIG. 1 is a blockdiagram of system 100, according to an embodiment of the invention. Asearch agent 102 may be provided. Search agent 102 may include one ormore modules such as, for example, a desktop integration module 104, anindex module 106, a graphical user interface module 108, and/or othermodules. Search agent 102 may be located at a user terminal 110. In someembodiments, certain modules such as, for example, index module 104 maybe implemented at user terminal 110, while other modules may beimplemented at user terminal 110 or remotely. Other variations may beused, as would be apparent.

User terminal 110 may include any one or more of for example, a desktopcomputer, a laptop or other portable computer, a hand-held computerdevice such as a Blackberry, a Personal Digital Assistant (PDA), and/orany other terminal device. User terminal device 110 may be connected toan enterprise portal server 112 over a network 114 via a communicationslink 116.

Server 112 may enable a user to remotely search for documents the userhas accessed, even if these documents are stored at the user's terminaldevice. Server 112 may be or include, for example, a workstation runningMicrosoft Windows™ NT™, Unix, Linux, Novell Netware™, and/or otheroperating systems. Network 114 may include any one or more networks,such as, for example, the Internet, an intranet, a Local Area Network(LAN), and/or other networks. Communications link 116 may include anyone or more communications links such as, for example, a coppertelephone line, a Digital Subscriber Line (DSL) connection, an Ethernetconnection, an Integrated Services Digital Network (ISDN) line, awireless connection, or other communications link.

Desktop integration module 104 may be provided to monitor documentsaccessed by a user for predetermined events. Desktop integration module104 may monitor any document that the user views, edits, creates,prints, downloads, or otherwise accesses. These predetermined events maybe or include, for example, opening a document, closing a document,printing a document, emailing a document, and/or other predeterminedevents.

Index module 106 may receive data from desktop integration module 104and put the data into a format that may be searched by a user using agraphical user interface. Index module 106 may enable a user to filtersearch results by, for example, a date or date range, a document type,and/or other parameters. A user may specify certain documents thatshould not be indexed, such as, for example, a default homepage or asearch index. Graphical user interface module 108 may provide agraphical user interface (GUI) that enables a user to search for apreviously accessed document.

A user may initiate a query from a search portlet located on the user'sportal page by using a traditional keyword search terms. The portalsoftware may then direct the query to index module 106 and searchresults may be presented to the user in a new graphical user interface.A graphical user interface for displaying search results and modifying asearch is described in detail hereinafter.

FIG. 2 illustrates an example of a portal page 200 having a searchportlet 202 embedded therein. If a user enters a keyword search intosearch portlet 202 and does not have the system software for searchingthe local index stores on their workstation, the software mayautomatically be downloaded from server 112. The user may be presentedwith a dialog box where the user may be asked if they would like toinstall the system. Once the user has consented to install thecomponents, the index and a control program are downloaded andinstalled. Once installed, the program may begin to create an index ofdocuments the user has accessed by searching well known browser cachesfor web documents and/or intercepting calls to known productivityapplications.

A desktop integration module may monitor predetermined events byretrieving content data and metadata from the applications used toaccess the documents. Metadata may refer to data describing an actiontaken by the user such as, for example, choosing a “document open” or a“document close” action. Metadata may also indicate the date and/or timea document was accessed. Content data may include data such as, forexample, words found in the document, keywords stored with the document,a name of the document, an author of the document, and/or other contentdata. In some embodiments, keywords may be specified by the user whencreating or modifying a document. In some embodiments, keywords may bedetermined by desktop integration module 104 based on the frequency ofoccurrence of certain words in the document.

According to one embodiment of the invention, desktop integration modulemay include one or more subsystems. FIG. 3 illustrates desktopintegration module 300, according to an embodiment of the invention.Desktop integration module 300 may include one or more modules such as,for example, an applications plugin module 302, a communications module304, a user interaction module 306, a document filter module 308, and/orother modules.

Application plugin module 302 may include one or more stand alonemodules which may be instantiated when an application matching aspecified type is started by the user or an operating system at theuser's terminal. Application plugin module 302 may extract informationfrom documents such as, for example, the document type, content as text,author, size, creation date, and/or other document information.Application module 302 may also collect information related to a user'saccess of or interaction with a document, such as, for example, whethera user forwards an email or other document, edits a document, prints adocument, and/or other user access.

Application plugin module 302 may be connected to communications module304 through a standard plugin interface. Communications module 304 maysubmit documents being retrieved from application plugin module 302 toindex module 106, enabling the documents to later be searched.Communications module 304 may convert documents into a format that canbe readily indexed, such as, for example, from a binary .DOC format to aXML format.

User interaction module 306 may monitor an amount of time a document isaccessed by the user. In some embodiments of the invention, userinteraction module 306 may be integrated with the operating system usedat the user's terminal to track the duration of a user's access of adocument. For example, in a Microsoft Windows operating environment,Windows application programming interfaces, which may register file openand close operation, may be used to track the duration of a user'saccess of a document.

In some embodiments of the invention, some documents need not be trackedand indexed by the system. Document filters module 308 may be used tofilter out documents that should not be tracked by the system. A usermay define filters based on a number of factors such as, for example,document type, uniform resource identifiers (URIs), and/or otherfactors. For example, documents in the Microsoft Money applicationformat may have personal financial information, so a user may wish todefine a filter for excluding these documents from the index. Documentshaving URIs known to contain personal information such as, for example,“c:Document Settings\User\Personal”, or documents having URIs beginningwith “https:\\” may be omitted. A user may also define filters fordocuments that are commonly accessed, such as a default browserhomepage, or a search engine such as Google. Plugin specific filters mayalso be defined for omitting documents, such as emails from certainaddresses, from being indexed.

FIG. 4 illustrates an example of the operation of desktop integrationmodule 300. At an operation 402, an application, such as, for example,Internet Explorer, may be started by a user. The user may click on theInternet Explorer icon to start up the browser. At an operation 404, anapplication plugin specific for Internet Explorer may start up. Theapplication plugin may search for a communications module, or start anew singleton process, at an operation 406. At an operation 408, thebrowser may open up to a default homepage. The application plugin wouldthen perform a filter check on the homepage URI to determine if thehomepage is one that should not be indexed, as illustrated at anoperation 410. As illustrated at an operation 412, if a filter has beenset up for the current URI, no information is gathered, and no indexentry is created. If no filter has been set up for the URI, anapplication plugin session may be created to track user activity, asillustrated at an operation 414. At an operation 416, user activityinformation may be collected and submitted to an index module.

According to one embodiment of the invention, graphical user interfacemodule 108 may provide a graphical user interface for displaying searchresults and enabling a user to enter additional search criteria. FIG. 5illustrates a graphical user interface 500, according to one embodimentof the invention. Following an initial keyword search execution viaportlet 202, GUI 500 may be presented having results set 502. Resultsdisplayed in results set 502 may be sorted in various ways such as, forexample, by relevance, document type, alphabetically, chronologically,and/or other sorting methods. Sorting menu 504 may be provided, enablinga user to select a desired sorting method.

A user may choose to view only documents of a certain type by selectingone or more document type filters 506. Additional keywords may beentered or a new search may be executed by entering search terms intoquery box 508. Selecting recall button 510 may enable a search to beperformed of all documents the user has previously accessed matching thesearch criteria.

In addition to standard search results displayed in search results box502, various graphical visualizations may be provided. A calendar 512may be provided. Calendar 512 may include indicia 514 indicating days onwhich documents from the search result set have been accessed. Indicia514 may indicate the first time a user has accessed a document, or inother embodiments may indicate each access by the user. As illustratedin FIG. 5, indicia 514 may include highlighting a particular calendarday or days. Other visual indicators may be used, as would be apparent.A user may restrict results displayed in search results box 502 byselecting one or more dates from calendar 512. Results box 502 entriesmay then be limited to documents which have been accessed on theselected dates.

A histogram 516 may be provided for controlling the result set in asimilar manner to calendar 512. A user may select either end of boundingbox 518 to dynamically revise the result set, showing only those resultswithin the selected date range. Histogram 516 may illustrate documentsmatching the search query in addition to all documents accessed by theuser, allowing the user to see which documents were used within whichsequence. For example, dark colored vertical lines 520 a may indicatedocuments that match the search criteria, while light colored verticallines 520 b may indicate all other documents the user has accessed.Other visual indications may be used, as would be apparent.

According to an embodiment of the invention, a user may retrieve achronological display of document usage. FIG. 6 illustrates a chronologyhistogram 600, according to this embodiment of the invention. Chronologyhistogram 600 may be provided wherein both results set documents andother used documents are shown as vertical bars on a horizontaltimeline. Horizontal timeline 602 provides a date range for whichchronology information may be obtained. This date range may be extendedby selecting and dragging the ends of bounding box 604 outward. The daterange may also be contracted by dragging the ends of bounding box 604inward.

In addition to the timeline on the horizontal axis, the height of eachbar may provide additional information to the user about a document. Theheight of vertical lines may indicate the relevance of each document tothe search query. In an alternative embodiment, the height of thevertical lines may indicate a specific usage pattern such as, forexample, the amount of time spent working in a specific document. Auser's usage activity may be recorded by Desktop Integration Module(shown in FIG. 1) and this information may be normalized to display ausage summary on chronology histogram 600.

Selecting a vertical line may open the selected document directly. Inother embodiments, selecting a vertical line may cause a popup window606 to be displayed. Pop-up window 606 may display a result set summaryfor the selected document. Summary information displayed in popup window606 may include, for example, the document name, document location,document type, a summary of the document content, and/or other documentrelated information.

According to one aspect of the invention, multiple variables may becharacterized on the vertical axis of a chronology histogram. FIG. 7illustrates a chronology histogram 700, according to this embodiment ofthe invention. Displaying multiple variables may enable a user toquickly and efficiently locate a desire document. As illustrated,chronology histogram 700 displays both relevance of search resultsdocuments to the entered keywords as well as the amount of time spentaccessing or interacting with the document. Other documentcharacteristics may be displayed such as, for example, the number ofhits.

Vertical axis 701 may provide multiple variables such as, for example, arelevance variable 702 and a duration variable 703. White boxes 704 maybe provided to illustrate the time a user has spent on a document. Thistime may be illustrated for all documents a user has accessed, whetheror not a particular document matches the search criteria. Shaded boxes706 may indicate the relevance of one or more documents matching thecriteria. Horizontal axis 708 may indicate one or more dates a documentwas accessed. Horizontal axis 708 may also indicate, chronologically,the order in which a document was accessed. In some embodiments of theinvention, horizontal axis 708 may provide a time display, indicatingthe time interval in which a document was accessed.

According to one aspect of the invention, relevance calculations forsearch results are enhanced for a specific user by collecting usermetrics during the user's interaction with the document. In addition toranking documents based on the frequency and location of keyword hitsand the proximity of query keyword hits to each other, the invention maycollect metadata using desktop integration module 104 (illustrated inFIG. 1). Collected metadata may include, for example, the amount of timespent on a document, how often a document has been viewed, or otherwiseaccessed, whether or not the document was printed or emailed, and/orother document related actions.

Certain criteria may be required in order to determine the amount oftime a user has spent interacting with a document. For example, it maybe a requirement that the user has the document open and in focus. Infocus may refer to having the selected document as the active windowwhen multiple documents and/or applications are open. A user may berequired to perform some type of input/output operation within apredetermined time interval in order for time calculation to continue.For example, the input/output operation may be a keystroke or mousemovement.

Once the criteria have been satisfied, the collected metadata may beentered into the index using index module 106 (illustrated in FIG. 1).Opening a document multiple times may cause metadata to be obtained forboth frequency and duration of use. For example, a document that hasbeen opened three times may show a frequency of three, and the totalamount of time spent among the three accesses may be combined tocalculate the amount of time the user has spent on the document.

According to another aspect of the invention, metrics regarding a user'sinteraction with one or more documents may be presented to the user on agraphical user interface. Presenting user metrics to the user may enablethe user to more readily distinguish between documents in the result setand simplify the process of finding the desired document.

In some embodiments of the invention, a user may trigger the userinterface to present user metrics by performing an action such as, forexample, right-clicking on the document in the result set. A pop-upwindow 802 may be provided, as illustrated in FIG. 8. Pop-up window 802may display, for example, document name, document location, the numberof times the document has been opened by the user, the total amount oftime the user has spent on the document, and/or other user metrics.

In some embodiments of the invention, user metrics may be displayed whena user hovers over a document in the result set. Hovering over adocument may cause a change in the calendar and/or histogram graphicalrepresentations. For example, as illustrated in FIG. 9, calendar 902 mayhighlight days on which the selected document has been accessed.Histogram 904 may provide additional user metrics. For example, thex-axis of histogram 904 may display the dates in which the user accessedthe selected document, while the y-axis illustrates the amount of timethe user spent on the document. Small icons, such as icons 906, may bepresented on histogram 904, indicating the amount of time the user spenton the document. Other icons may also be presented, for example, aprinter icon, book icon, and/or envelope icon may be presented toindicate that the user has printed, read, and/or emailed the document,respectively. Other icons may be presented indicating editing of adocument, forwarding, replying, and/or other document related actions,as would be apparent.

While certain actions have been described above, other actions may beused to present user metrics to the user. For example, a user may singleclick on a document to change the views of the histogram and calendar,or the user may double click on a document to open a new windowproviding user statistics.

According to an embodiment of the invention, user metrics may beprovided directly in the results set without requiring additionalactions to be performed. FIG. 10 illustrates a result set 1000 whichprovides user metrics. User metrics illustrated in result set 1000 mayinclude, for example, the total viewing time for each document, theamount of time the document was viewed, and the date the document waslast accessed. Other user metrics may be provided, as would be apparent.

According to another aspect of the invention, the system may beintegrated into a user's email and calendar application. A user mayquickly obtain documents relevant to a particular email message orcalendar entry. A user interface for searching based on a user's emailand calendar entries may be integrated with the email applications insome embodiments, or may be a standalone application.

FIG. 11 illustrates an example of a calendar view 1100 associated withan email program such as, for example, Lotus Notes. As illustrated,several meetings 1110 are listed on calendar 1100. A user wishing toview documents related to a scheduled meeting may do so by selecting themeeting and choosing an option to search for related documents. Optionsmay be provided by various ways, such as, for example, “right-clicking”on a meeting to bring up a pop-up menu, choosing an option from Actionsmenu 1112, or other methods as would be apparent. Search criteria mayalso be created from an email message. Search criteria may include, forexample, the title of the meeting, subject of the email message,keywords from the body of an email message, names of meeting invitees,and/or other criteria.

Desktop integration module 102 may obtain content and metadata fromcalendar 1100 regarding the selected meeting. Indexing module 104 mayuse the retrieved metadata and content data and compare it to theindexed data for all stored documents. Documents having matching contentdata and/or metadata may be returned as being related to the selectedmeeting. In other embodiments, authors of documents may associate thedocument with certain meetings. In some embodiments of the invention,only documents accessed on the day of the meeting are retrieved while inother embodiments, all accessed documents related to the meeting arereturned.

Once the user has been presented with search results, the user maymodify the search to more quickly find desired documents. For example,the user may input additional keywords, use document type filters toreturn only documents of certain types, restrict the search to one ormore dates, and/or other search modifications.

According to another aspect of the invention, a system may be provided,enabling a user to search a local workstation from a remote portallocation. As used herein, local workstation may refer to the workstationthat is assigned to a particular user and from which the user typicallyworks. A user may have access to documents stored on their local deviceand may be able to integrate these documents into a portal integrationenvironment.

As described above, in some embodiments of the invention, an index andcontrol program may be downloaded to a user's workstation the first timea query is made using the portlet. In addition to the index and controlprograms, a web responder may also be installed. FIG. 12 illustrates ablock diagram 1200 of the system including web responder 1202. In someembodiments of the invention, web responder 1202 listens for inboundqueries from Enterprise Portal Server 1204 over network 1206. Once webresponder 1202 has been installed, queries from Enterprise Portal Server1204 may be accepted at user terminal 1210.

A user may perform a search from Enterprise Portal Server 1204 in amanner similar to performing a local search. The user may enter a searchquery into a portal page, such as the portal illustrated in FIG. 2. Thequery may then be sent to the local workstation where the web responderhas been installed. An index at user terminal 1210 may then process thequery and return the results in a format supported by Enterprise PortalServer 1204, such as, for example, the XML format. Results may then beformatted and presented to the user.

According to one embodiment of the invention, searching a localworkstation index may be performed as a part of a search from anotherapplication. For example, a single search may be used to search a user'sworkstation, email documents, and/or a corporate document managementsystem using a search engine integrated with the document managementsystem. Search results may be combined into one display. In analternative embodiment, only the user's own documents are searched usingthe index at the user's workstation.

While particular embodiments of the invention have been described, it isto be understood that modifications will be apparent to those skilled inthe art without departing from the spirit of the invention. The scope ofthe invention is not limited to the specific embodiments describedherein. Other embodiments, uses and advantages of the invention will beapparent to those skilled in art from consideration of the specificationand practice of the invention disclosed herein. The specification shouldbe considered exemplary only, and the scope of the invention isaccordingly intended to be limited by the following claims.

1. A computer-implemented apparatus for generating an automatic searchquery for an electronic mail application integrating an electroniccalendar system comprising: a processor configured to: monitor documentswith which a user has interacted; obtain content data and metadata fromthe monitored documents; create an index of documents with which theuser has interacted by indexing the content data and metadata obtainedfrom the monitored documents; receive an input comprising auser-selected calendar entry from the electronic calendar system; inresponse to receiving the user-selected calendar entry, automaticallygenerate a search query from the user-selected calendar entry to searchthe index of documents with which the user has interacted for one ormore documents related to the selected calendar entry; execute saidsearch query by locating one or more documents in the index of documentswith which the user has interacted that are related to the selectedcalendar entry; and provide search results to the user, wherein thesearch results include the one or more documents located during theexecution of the search query.
 2. The apparatus of claim 1 whereinprovide said search results further comprises: provide a user interfacehaving a list of documents matching said search query; and provide asearch entry field enabling the user to enter one or more additionalkeywords to refine said search results.
 3. The apparatus of claim 1wherein the search results include only monitored documents that theuser has interacted.
 4. The apparatus of claim 1 wherein monitoringdocuments with which the user has interacted includes filtering outdocuments that the user has indicated should not to be monitored orindexed.
 5. The apparatus of claim 1 wherein executing the search queryincludes remotely searching a user terminal from an internet portal. 6.A computer-implemented apparatus for generating an automatic searchquery from an electronic mail application integrating with an electroniccalendar system comprising: a processor configured to: receive an inputcomprising a user-selected calendar entry from the electronic calendarsystem; in response to receiving the user-selected calendar entry,automatically generate a search query from the user-selected calendarentry to search a local index of documents that the user has previouslyaccessed for one or more documents related to the selected calendarentry; execute said search query by locating one or more documents inthe local index that are related to the selected calendar entry; andprovide search results in response to said search query to the user,wherein the search results include the one or more documents in thelocal index that were located during the execution of the search query.7. The apparatus of claim 6 wherein executing the search query includesremotely searching a user terminal from an Internet portal.
 8. Theapparatus of claim 6 where the search results include only documentsthat the user has previously accessed.
 9. The apparatus of claim 6wherein automatically generating a search query further comprisesretrieving metadata from said selected calendar entry and using saidmetadata to create the search query, wherein said metadata includes oneor more of a title of the calendar entry, one or more meeting attendees,and one or more keyword from a body portion of said calendar entry. 10.The apparatus of claim 6 wherein providing said search results furthercomprises: providing a user interface having a list of documentsmatching said search query; and providing a search entry field enablingthe user to enter one or more additional keywords to refine said searchresults.